What do you think about enhancing Environment such that it inherently supports retrieving an ordered Collection of property values?

It could then be up to the GuacamoleProperty implementation to decide how to represent multiple values (if at all).

Sounds good - I will take a look.

@mike-jumper Okay, I've started down path that I think is approximately what you're suggesting, while trying to avoid breaking everything in the process. So, instead of making getProperty() and/or getRequiredProperty() return a collection, I added a new set of methods, getPropertyCollection() and getRequiredPropertyCollection() that are intended to parse into a Collection.

This would rely on each of the properties to implement a new getValueCollection() method, which I've provided a default implementation for in GuacamoleProperty that basically says "not yet implemented."

Let me know if this looks good, sane, reasonable, etc., or if there's a better solution? I could break everything and make getValue(), getProperty(), and getRequiredProperty() return collections instead of individual values, if that's preferable?

@mike-jumper Okay, I've re-worked the implementation, here, providing support within the existing property classes for parsing and retrieving lists of values.

default implementations for new functions were added to the GuacamoleProperty interface, but I think they're missing from Environment.

Otherwise, LGTM!

Okay, I think I managed to get these default methods implemented correctly in the Environment interface, but for some reason it was a bit of a mind-bending exercise on the order of the spoon in The Matrix.